Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Reset current scene now prefers using Tank Apps for saving. #11

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Reset current scene now prefers using Tank Apps for saving. #11

wants to merge 2 commits into from

Conversation

tonybarbieri
Copy link

Reset current scene will try to use Tank Apps before resorting to the built in platform method.

Introduces the scene_modified scene operation hook.
The reset scene operation hook will now force a reset. The check for modification has been moved up the chain to the caller.

Requires pull request: shotgunsoftware/tk-multi-snapshot#5 which adds a return value from the snapshot dialog command. This is necessary to check for user cancelled.

@alandann
Copy link
Contributor

Hi Tony,

We're not too sure about this one :P

It feels like some of this is a workflow that is quite specific for you guys - particularly the snapshot instead of just performing a save. I can see it using Shotgun Save-As as being sensible but this could possibly be done in the hook instead? This is also something we can consider when looking at Context 2.0...

Could you explain a bit more about the reasoning behind it and the problem it's aiming to solve - we can have a quick chat if that would be more useful?

Thanks
Alan

@tonybarbieri
Copy link
Author

Well the way I see it is, these tools have been developed to save your
workfiles. Why then would the applications save dialog be used when a user
is prompted to save when changing context, starting a new scene, etc. and
not use the Tank save tools? The application save tools are always
available so a user could simply cancel and save using those if necessary.
I would think we'd want the pipeline save tools (Save As, Snapshot) to be
used as much as possible.

On Fri, Aug 23, 2013 at 8:23 AM, alandann [email protected] wrote:

Hi Tony,

We're not too sure about this one :P

It feels like some of this is a workflow that is quite specific for you
guys - particularly the snapshot instead of just performing a save. I can
see it using Shotgun Save-As as being sensible but this could possibly be
done in the hook instead? This is also something we can consider when
looking at Context 2.0...

Could you explain a bit more about the reasoning behind it and the problem
it's aiming to solve - we can have a quick chat if that would be more
useful?

Thanks
Alan


Reply to this email directly or view it on GitHubhttps://github.com//pull/11#issuecomment-23160175
.

-tony

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants